RE: Accidentally Delete *.dbf Files, OH NO!!!

  • From: "Eric Buddelmeijer" <Eric.Buddelmeijer@xxxxxxxxxx>
  • To: <mfontana@xxxxxxxxx>, <Oracle-L@xxxxxxxxxxxxx>
  • Date: Tue, 1 Feb 2005 18:29:30 +0100

Michael,

I Like one suggestion earlier in this thread about fuser. I have been trying
to get our sa's to incorporate it in some sort of wrapping for rm (alias,
link, function or other). Precisely because fuser will tell you if a user,
and even which one is using a file. Problem is I can't do it myself because
you need root privileges to use fuser, at least on the versions of solaris I
have seen (2.8 and 2.9). And the sa's have not found the time to work around
that. But there is also a chance fuser will not tell you that the file is
being used because it in fact it is not. Oracle might not have each and
every file opened. And the database could be down as well. 
Having said all that, maybe communication with your colleaques is the best
solution. Tell them when you put some essential files in an unlikely place.
So they know the files must not be deleted.

Eric.

-----Original Message-----
From: Michael Fontana [mailto:mfontana@xxxxxxxxx]
Sent: Monday, January 31, 2005 6:23 PM
To: Oracle-L@xxxxxxxxxxxxx
Subject: Accidentally Delete *.dbf Files, OH NO!!!


I have been working with Solaris for several years now.  We have had a
rare
but particularly debilitating problem where certain people who will
remain
nameless, in an effort to "clean up" disk space, have nailed a .dbf file
or
two.  I know I should have the solution to this on close at hand, but I
seem
to recall this was difficult, if not impossible, on other Unix platforms
(such as AIX), because the file would be "locked" or "in use", and the
nefarious "rm" command would fail.  Alas, Solaris is all too willing to
comply when asked.  

Is there something that can be done, at the OS or Oracle level, to
prevent
such a thing?  Needless to say, the "whackers" are using root to enter
the
command, so changing permissions would accomplish little.  They are
already
set to only allow "oracle" write access.

Any help or even ridiculing chuckles and admonitions would be greatly
appreciated.



--
//www.freelists.org/webpage/oracle-l

--
//www.freelists.org/webpage/oracle-l


--
//www.freelists.org/webpage/oracle-l

Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 02-2005